Default Value Display Logic Updated for Candidate Fields

Parser

What’s changed?

We’ve resolved an issue where certain fields were automatically populated with Bullhorn’s hardcoded default values when a new Candidate record was created via the Automatic Resume Parser, despite no default being set in the client’s fieldmaps. Now, these fields will remain empty unless a client explicitly sets a default value, improving data accuracy and alignment with configured preferences.

Due to database requirements, the following fields cannot be empty and will default to the following values (consistent with manual resume parsing):

• willRelocate defaults to false

• isEditable defaults to true

• categoryID defaults to a value representing “Other(s)” if no category can be derived from the candidate’s occupation.

For more information, see Automatic Resume Parser.